-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Merge 21.3 fixes & editorialized release notes to trunk #19698
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ht-local-drafts-check Move local drafts check to ContentMigrationCoordinator
…ect-wp [Jetpack Migration Flow] [Jetpack] Determine if WordPress app is installed
…ect-migratable-wp [Jetpack Migration Flow] [Jetpack] Determine if installed WordPress version is capable of Jetpack migrations
…efaults Add import logic to `JetpackWindowManager`
…l-posts Check all posts remote status instead of just drafts
…on-track-wp-compatibility Jetpack migration flow - add tracks for migratable and not migratable statuses
…elease_1.85.1 Integrate gutenberg-mobile release 1.85.1
…4-to-release/21.3
…ease/21.3 Merge 21.2.0.4 to release/21.3
Contributor
You can test the changes in WordPress from this Pull Request by:
|
Contributor
You can test the changes in Jetpack from this Pull Request by:
|
… first launch (#19697) When launching the app registerForRemoteNotifications() is called. It checks shouldPresentNotifications() to determine whether app should register for notifications or not. shouldPresentNotifications() should return true if notifications where never toggled
Generated by 🚫 dangerJS |
jkmassel
approved these changes
Dec 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've not yet created the second betas as I am waiting for some PRs against
release/21.3to create them, but I wanted to merge the changes inrelease/21.3so far totrunkto avoid possible merge conflicts.This PR includes changes to
release/21.3made in #19681, #19655, #19680, #19676, #19684, #19692, #19690, #19689, #19695 & #19697Update: It also includes the editorialized release notes.